The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 30, 2026 9:58pm

@greptile review

@BugBot review

PR Summary

Low Risk
Primarily refactors logging (levels and structured metadata) across request handlers and executor paths; functional behavior is largely unchanged aside from when/where some IDs are generated for logging context.

Overview
Improves observability by standardizing structured logging across Copilot chat APIs, Mothership endpoints, and workflow execution.

Replaces appendCopilotLogContext(...) string concatenation with logger.withMetadata(...) and generally shifts many success-path logs from error to info/warn, while preserving error logging for actual failures.

Adds consistent request-scoped metadata (requestId, messageId, and for workflow execution also workflowId, workspaceId, userId, executionId) throughout /workflows/[id]/execute, the executor (DAGExecutor, ExecutionEngine, BlockExecutor), and streaming/orchestrator code; updates affected tests to mock withMetadata.

^{Written by Cursor Bugbot for commit bb5702a. This will update automatically on new commits. Configure here.}

Greptile Summary

Adds withMetadata() to the Logger class so structured context is automatically included in log lines. Applied across the execute route, executor classes, ExecutionLogger, and copilot tooling routes — replacing the old appendCopilotLogContext helper and fixing many logger.error() calls used for routine informational events.

Notable changes:

• Logger package: withMetadata(metadata) returns an immutable child logger with merged key-value pairs. Full unit tests added.
• Executor classes gain an execLogger field initialised from execution context in each constructor.
• Execute route builds up reqLogger progressively, replacing [requestId] string interpolation.
• ExecutionLogger uses metadata-bound loggers throughout, addressing a prior review comment.
• Minor: two logger.warn() calls in generate-visualization.ts and one logger.error() in user-table.ts still use the bare module logger instead of the local reqLogger, losing messageId context on those lines.

Confidence Score: 5/5

• Safe to merge — no logic errors or data correctness issues; only minor style inconsistencies remain.
• All findings are P2: two log calls in generate-visualization.ts and one in user-table.ts use the bare module logger instead of the enriched reqLogger, losing messageId context on those lines. These are observability nits with no impact on correctness or runtime behaviour. The core Logger.withMetadata implementation is clean, well-tested, and correctly applied across the vast majority of the codebase.
• apps/sim/lib/copilot/tools/server/visualization/generate-visualization.ts (lines 98, 134) and apps/sim/lib/copilot/tools/server/table/user-table.ts (line 247) — bare logger used instead of local reqLogger.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Route as execute/route.ts
    participant Logger as Logger (module)
    participant Child1 as reqLogger {requestId, workflowId}
    participant Child2 as reqLogger {+userId, executionId}
    participant Child3 as reqLogger {+workspaceId}
    participant Executor as DAGExecutor / Engine / BlockExecutor

    Route->>Logger: withMetadata({requestId, workflowId})
    Logger-->>Child1: child logger
    Route->>Child1: info("Starting server-side execution")
    Route->>Child1: withMetadata({userId, executionId})
    Child1-->>Child2: merged child logger
    Route->>Child2: error("Workflow has no workspaceId") [if missing]
    Route->>Child2: withMetadata({workspaceId})
    Child2-->>Child3: merged child logger
    Route->>Child3: info("Preprocessing passed")
    Route->>Executor: new DAGExecutor(contextExtensions)
    Executor->>Logger: withMetadata({workflowId, workspaceId, executionId, userId, requestId})
    Logger-->>Executor: execLogger stored as field
    Executor->>Executor: execLogger.info / warn / error (all log lines carry full context)

_{Reviews (4): Last reviewed commit: "Merge branch 'staging' into feat/improve..." | Re-trigger Greptile}

@greptile review

@greptile review

@BugBot review